Unit of Competency Mapping – Information for Teachers/Assessors – Information for Learners

ICTSAS402 Mapping and Delivery Guide
Implement configuration management strategies

Version 1.0
Issue Date: May 2024


Qualification -
Unit of Competency ICTSAS402 - Implement configuration management strategies
Description
Employability Skills
Learning Outcomes and Application This unit describes the skills and knowledge required to implement administrative and technical procedures throughout the software development and documentation life cycle.It applies to individuals working in a range of information and communications technology (ICT) development environments who have responsibility to ensure work is completed to quality standards and technical requirements.No licensing, legislative or certification requirements apply to this unit at the time of publication.
Duration and Setting X weeks, nominally xx hours, delivered in a classroom/online/blended learning setting.

Gather evidence to demonstrate consistent performance in conditions that are safe and replicate the workplace. Noise levels, production flow, interruptions and time variances must be typical of those experienced in the systems administration and support field of work and include access to:

special purpose tools, equipment and materials

industry software packages

configuration tools

evaluation criteria

process for approval of change requests

templates for status reports.

Assessors must satisfy NVR/AQTF assessor requirements.
Prerequisites/co-requisites
Competency Field
Development and validation strategy and guide for assessors and learners Student Learning Resources Handouts
Activities 		Slides
PPT 		Assessment 1 Assessment 2 Assessment 3 Assessment 4
Elements of Competency Performance Criteria              
Element: Identify and clarify configuration management requirements
  • Develop and assemble identification standards for the naming and version control of software and documentation, and provide to stakeholders
  • Identify software configuration tools and procedures for the required level of integration into the programming environment
  • Identify responsibilities for configuration management within the project and for ongoing support, including approval of changes
  • Take action to ensure that stakeholders are aware of their roles
  • Identify point at which items are subjected to configuration control with stakeholders
       
Element: Employ appropriate control mechanisms
  • Identify and document method for identification and recording of change requests in line with organisational requirements, and ensure this is maintained during development process
  • Take action to ensure evaluation criteria and process for approval of change requests are employed according to organisational requirements
  • Take action to ensure other management, security and access control criteria are employed according to organisational requirements
  • Implement controls to ensure that necessary audit trials and alerts for variations or non-conformance are continuously maintained during development
       
Element: Implement monitoring mechanisms
  • Implement controls to ensure mechanisms to identify software status throughout the software development life cycle are continuously maintained
  • Document development and maintenance of records and status reports required to show the history of baselines and their links to backups
  • Take action to ensure level of detail required in status reports, and identification of target audiences, meet the configuration management procedures, International Organization for Standardization (ISO), International Electrotechnical Commission (IEC) and Australian Standards (AS) and organisational requirements
  • Integrate configuration management into general project management processes for monitoring and control purposes and document
       
Element: Manage release of product
  • Take action to ensure physical and functional completeness of items for release to all stakeholders
  • Identify and implement requirements for formal control of software products
  • Determine and document policies for retention of baseline or master copies, taking into account safety and security, legislative requirements and organisational guidelines
       


Evidence Required

List the assessment methods to be used and the context and resources required for assessment. Copy and paste the relevant sections from the evidence guide below and then re-write these in plain English.

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Identify and clarify configuration management requirements

1.1 Develop and assemble identification standards for the naming and version control of software and documentation, and provide to stakeholders

1.2 Identify software configuration tools and procedures for the required level of integration into the programming environment

1.3 Identify responsibilities for configuration management within the project and for ongoing support, including approval of changes

1.4 Take action to ensure that stakeholders are aware of their roles

1.5 Identify point at which items are subjected to configuration control with stakeholders

2. Employ appropriate control mechanisms

2.1 Identify and document method for identification and recording of change requests in line with organisational requirements, and ensure this is maintained during development process

2.2 Take action to ensure evaluation criteria and process for approval of change requests are employed according to organisational requirements

2.3 Take action to ensure other management, security and access control criteria are employed according to organisational requirements

2.4 Implement controls to ensure that necessary audit trials and alerts for variations or non-conformance are continuously maintained during development

3. Implement monitoring mechanisms

3.1 Implement controls to ensure mechanisms to identify software status throughout the software development life cycle are continuously maintained

3.2 Document development and maintenance of records and status reports required to show the history of baselines and their links to backups

3.3 Take action to ensure level of detail required in status reports, and identification of target audiences, meet the configuration management procedures, International Organization for Standardization (ISO), International Electrotechnical Commission (IEC) and Australian Standards (AS) and organisational requirements

3.4 Integrate configuration management into general project management processes for monitoring and control purposes and document

4. Manage release of product

4.1 Take action to ensure physical and functional completeness of items for release to all stakeholders

4.2 Identify and implement requirements for formal control of software products

4.3 Determine and document policies for retention of baseline or master copies, taking into account safety and security, legislative requirements and organisational guidelines

Evidence of the ability to:

identify and clarify configuration management requirements

identify and action control mechanisms

implement administrative and technical procedures

maintain reliable and valid technical and administrative procedures

use quality processes, audit trails and version control.

Note: Evidence must be provided for at least TWO situations or organisations.

To complete the unit requirements safely and effectively, the individual must:

compare and contrast project planning methodologies and tools

explain benchmarking methodologies when implementing monitoring mechanisms

describe how to formulate software size models and size estimates when employing control mechanisms

discuss quality assurance and quality processes when implementing monitoring mechanisms

describe software development methodologies when identifying and clarifying configuration management requirements

identify and summarise relevant organisational guidelines, legislation and codes of practice.

Submission Requirements

List each assessment task's title, type (eg project, observation/demonstration, essay, assignment, checklist) and due date here

Assessment task 1: [title]      Due date:

(add new lines for each of the assessment tasks)

Assessment Tasks

Copy and paste from the following data to produce each assessment task. Write these in plain English and spell out how, when and where the task is to be carried out, under what conditions, and what resources are needed. Include guidelines about how well the candidate has to perform a task for it to be judged satisfactory.

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Identify and clarify configuration management requirements

1.1 Develop and assemble identification standards for the naming and version control of software and documentation, and provide to stakeholders

1.2 Identify software configuration tools and procedures for the required level of integration into the programming environment

1.3 Identify responsibilities for configuration management within the project and for ongoing support, including approval of changes

1.4 Take action to ensure that stakeholders are aware of their roles

1.5 Identify point at which items are subjected to configuration control with stakeholders

2. Employ appropriate control mechanisms

2.1 Identify and document method for identification and recording of change requests in line with organisational requirements, and ensure this is maintained during development process

2.2 Take action to ensure evaluation criteria and process for approval of change requests are employed according to organisational requirements

2.3 Take action to ensure other management, security and access control criteria are employed according to organisational requirements

2.4 Implement controls to ensure that necessary audit trials and alerts for variations or non-conformance are continuously maintained during development

3. Implement monitoring mechanisms

3.1 Implement controls to ensure mechanisms to identify software status throughout the software development life cycle are continuously maintained

3.2 Document development and maintenance of records and status reports required to show the history of baselines and their links to backups

3.3 Take action to ensure level of detail required in status reports, and identification of target audiences, meet the configuration management procedures, International Organization for Standardization (ISO), International Electrotechnical Commission (IEC) and Australian Standards (AS) and organisational requirements

3.4 Integrate configuration management into general project management processes for monitoring and control purposes and document

4. Manage release of product

4.1 Take action to ensure physical and functional completeness of items for release to all stakeholders

4.2 Identify and implement requirements for formal control of software products

4.3 Determine and document policies for retention of baseline or master copies, taking into account safety and security, legislative requirements and organisational guidelines

Copy and paste from the following performance criteria to create an observation checklist for each task. When you have finished writing your assessment tool every one of these must have been addressed, preferably several times in a variety of contexts. To ensure this occurs download the assessment matrix for the unit; enter each assessment task as a column header and place check marks against each performance criteria that task addresses.

Observation Checklist

Tasks to be observed according to workplace/college/TAFE policy and procedures, relevant legislation and Codes of Practice Yes No Comments/feedback
Develop and assemble identification standards for the naming and version control of software and documentation, and provide to stakeholders 
Identify software configuration tools and procedures for the required level of integration into the programming environment 
Identify responsibilities for configuration management within the project and for ongoing support, including approval of changes 
Take action to ensure that stakeholders are aware of their roles 
Identify point at which items are subjected to configuration control with stakeholders 
Identify and document method for identification and recording of change requests in line with organisational requirements, and ensure this is maintained during development process 
Take action to ensure evaluation criteria and process for approval of change requests are employed according to organisational requirements 
Take action to ensure other management, security and access control criteria are employed according to organisational requirements 
Implement controls to ensure that necessary audit trials and alerts for variations or non-conformance are continuously maintained during development 
Implement controls to ensure mechanisms to identify software status throughout the software development life cycle are continuously maintained 
Document development and maintenance of records and status reports required to show the history of baselines and their links to backups 
Take action to ensure level of detail required in status reports, and identification of target audiences, meet the configuration management procedures, International Organization for Standardization (ISO), International Electrotechnical Commission (IEC) and Australian Standards (AS) and organisational requirements 
Integrate configuration management into general project management processes for monitoring and control purposes and document 
Take action to ensure physical and functional completeness of items for release to all stakeholders 
Identify and implement requirements for formal control of software products 
Determine and document policies for retention of baseline or master copies, taking into account safety and security, legislative requirements and organisational guidelines 

Forms

Assessment Cover Sheet

ICTSAS402 - Implement configuration management strategies
Assessment task 1: [title]

Student name:

Student ID:

I declare that the assessment tasks submitted for this unit are my own work.

Student signature:

Result: Competent Not yet competent

Feedback to student

 

 

 

 

 

 

 

 

Assessor name:

Signature:

Date:

Assessment Record Sheet

ICTSAS402 - Implement configuration management strategies

Student name:

Student ID:

Assessment task 1: [title] Result: Competent Not yet competent

(add lines for each task)

Feedback to student:

 

 

 

 

 

 

 

 

Overall assessment result: Competent Not yet competent

Assessor name:

Signature:

Date:

Student signature:

Date: